Update haml_lint 0.57.0 → 0.58.0 (major) #1483
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ haml_lint (0.57.0 → 0.58.0) · Repo · Changelog
Release Notes
0.58.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 10 commits:
Cut version 0.58.0 (#506)
Update rubocop requirement from 1.63.1 to 1.63.3 (#504)
Fix `block_keyword` method returning keywords used as arguments of method call (#505)
Update rubocop requirement from 1.62.1 to 1.63.1 (#503)
Update rubocop-performance requirement from 1.20.2 to 1.21.0 (#501)
Update rubocop requirement from 1.61.0 to 1.62.1 (#499)
Update rubocop requirement from 1.60.2 to 1.61.0 (#498)
Update README.md to reflect new options (#497)
Feature: introduce RuboCop performance (#494)
Update overcommit requirement from 0.62.0 to 0.63.0 (#496)
✳️ rubocop (1.63.2 → 1.63.4) · Repo · Changelog
Release Notes
1.63.4
1.63.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 25 commits:
Cut 1.63.4
Update Changelog
Fix an error for `rubocop -V` when `.rubocop.yml` contains ERB
Merge pull request #12866 from amomchilov/rescue-GemfileNotFound
Merge pull request #12867 from koic/fix_false_positive_for_style_redundant_line_continuation
[Fix #12865] `require 'bundler'` if possible, but…
[Fix #12862] Fix a false positive for `Style/RedundantLineContinuation`
Merge pull request #12664 from muxcmux/master
Merge pull request #12863 from Uaitt/cli-options-missing-periods
Add missing periods on CLI options descriptions
Tweak the infinite loop error message
Reset the docs version
Cut 1.63.3
Update Changelog
Make `InternalAffairs/ExampleDescription` aware of an improper description
Remove redundant braces in a few uses of `def_node_matcher`
Fix false negatives for `Lint/UnreachableCode`
[Fix #12848] Fix an error for `RuboCop::Lockfile`
Set custom program name for the built-in LSP server
Merge pull request #12856 from koic/workaround_for_prism_0_26
Workaround for incompatibilities between Prism 0.25.0 and 0.26.0
Merge pull request #12853 from Earlopain/global-offense-cache
[Fix #12852] Correctly deserialize a global offense
Tweak examples for `Style/Send`
Reset the docs version
Commits
See the full diff on Github. The new version differs by 9 commits:
Update changelog.
Bump version.
* Bump parser branches to 3.0.7, 3.1.5, 3.2.4, 3.3.1 (#1011)
+ ruby{33,34}.y: allow blocks inherit anonymous args. (#1010)
`action.rb` doc fixes (#1008)
* Use `require_relative` in the Parser codebase (#1003)
Use `AST::Processor::Mixin` instead of deprecated `AST::Processor` (#1000)
+ Raise a more specific error when encountering an unknown magic comment encoding (#999)
Update changelog.
Commits
See the full diff on Github. The new version differs by 8 commits:
Cut 1.31.3
Update Changelog
Handle encoding error from the parser gem
Workaround for incompatibilities between Prism 0.24.0 and 0.25.0 (#290)
Update org name from rubocop-hq to rubocop
Suppress a RuboCop's offense
Add CHANGELOG entry.
Restore docs/antora.yml
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands